lifi: include Jumper volume (remove integrator exclusion) - #8972
Open
Octave-byte wants to merge 1 commit into
Open
lifi: include Jumper volume (remove integrator exclusion)#8972Octave-byte wants to merge 1 commit into
Octave-byte wants to merge 1 commit into
Conversation
The LI.FI bridge and swap adapters no longer exclude the Jumper integrators (jumper.exchange, transferto.xyz, jumper.exchange.gas, lifi-gasless-jumper), so they report total LI.FI volume including Jumper on both the on-chain and analytics-API paths. The separate jumper.exchange / jumper-exchange adapters are intentionally left in place so Jumper is still reported on its own. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 2 included reviews per hour; 1 remains after this review. Summary by CodeRabbit
WalkthroughLiFi volume aggregation now counts all integrators, including Jumper, across Bitcoin and Solana API results and qualifying on-chain swap or bridge events. ChangesLiFi integrator volume
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This localized change updates LI.FI volume reporting to include Jumper integrations, with no actionable merge-blocking risk remaining beyond normal checks and review. Suggested labels: 🚥 Pre-merge checks | ✅ 14 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (14 passed)
✨ Finishing Touches 💡 1⚔️ Resolve merge conflicts 💡
✨ Simplify code
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
bheluga
reviewed
Aug 24, 2026
bheluga
left a comment
bheluga
left a comment
Member
There was a problem hiding this comment.
@Octave-byte thanks for the PR
We count those volumes in jumper aggregator and bridge aggregator (https://defillama.com/protocol/jumper-(li.fi-powered)).
So that would be double counted right?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The LI.FI bridge (
bridge-aggregators/lifi) and swap (aggregators/lifi) adapters currently exclude the Jumper integrators (jumper.exchange,transferto.xyz,jumper.exchange.gas,lifi-gasless-jumper). This removes that exclusion on both the on-chain and analytics-API paths, so the LI.FI adapters report total LI.FI volume including Jumper.The separate
jumper.exchange/jumper-exchangeadapters are intentionally left unchanged, so Jumper is still reported on its own.